Bahasa Pemrograman Rust: Dasar-Dasar Koleksi yang Dialokasikan di Heap

Arsitektur Pertumbuhan

Koleksi Rust, seperti Vec<T> dan String, bukan tipe dasar; mereka adalah struktur yang didefinisikan dalam pustaka dan berada di modul std modul. Fondasi ini menentukan bagaimana Rust mengelola data melalui sistem modul dan mengelola memori melalui RAII (Akses Sumber Daya adalah Inisialisasi). Sementara tipe sederhana berada di stack, koleksi menggunakan Penyimpanan Heap untuk pertumbuhan dinamis, artinya memori mereka harus dikelola secara eksplisit melalui Drop trait.

Resolusi Modul & Visibilitas

Kompiler Rust memetakan pohon modul dimulai dari akar krate (src/lib.rs atau src/main.rs). Deklarasi seperti mod front_of_house; memicu kompiler untuk mencari src/front_of_house.rs atau src/front_of_house/mod.rs. Menggunakan pub modifier dan pengalihan ulang (pub use) memungkinkan data yang dialokasikan di heap dan terenkapsulasi untuk diakses dengan aman melalui jalur yang sesuai gaya.

Segera setelah lingkup suatu modul berakhir, implementasi Drop secara otomatis mengembalikan memori heap: $$Memory_{dikembalikan} = \sum Drop(Elemen)$$.

TERMINALbash — 80x24

> Ready. Click "Run" to execute.

QUESTION 1

What happens if a project contains both src/module.rs and src/module/mod.rs?

The compiler prioritizes the directory style.

It triggers a compiler error due to ambiguity.

The files are merged automatically.

Rust ignores the .rs file.

QUESTION 2

How does RAII ensure memory safety in collections?

By using a background garbage collector.

By checking references at runtime.

By tying heap memory to the scope of the owner variable.

By keeping all data on the stack.

QUESTION 3

Which file is considered the 'anchor' for module resolution in a library crate?

src/main.rs

$src/lib.rs$

mod.rs

Cargo.toml

QUESTION 4

What is the purpose of the pub use statement?

To allocate memory on the heap.

To re-export a name to provide a more idiomatic public API.

To private-label a module.

To increase compilation speed.

QUESTION 5

Why can't Collections like Vec be stored entirely on the stack?

The stack cannot store integers.

They must have a fixed size known at compile time to stay on the stack.

The stack is too slow for collections.

Stack memory is never dropped.